A modern pipeline for academic collaboration

0.1 Rationale

As scientists, we spend a lot of time coding and writing.

Unfortunately, both activities involve repetitive behaviors and suboptimal routines…

For example, we might…

  • Duplicate our manuscript many times during co-edition
  • Struggle with references and bibliographies
  • Spend hours (days) reformating papers for resubmissions
  • Paste many variants of a figure in our presentation/report
  • Spend way to much title aligning items on Powerpoint
  • Feel like it is a big effort to put together a few slides or a report to describe our results
  • Have no idea of how we could participate or animate large-scale collaborations ! 🤪

0.2 Time wasted reduces your happiness

And this is particularly true when it comes with collaborating with our peers.

0.3 What prevents us from collaborating more smoothly?

  • Endless multiplication of communication channels (Mattermost 😇)

  • Data and code on local computers

  • Suboptimal coding practices (no virtual envs, no version control, absolute paths)

  • Lack of knowledge regarding others interests, skills and activities

  • Dependence upon Google Docs is increasingly problematic

    • And Google Docs is not even great

  • Unnecessary differences in software use.

  • …?

0.4 A (tiny) reason to hope!

Most Cophy-makers already use Zotero or are willing to change. Users of Latex will be fine anyways.

0.5 A (bigger) reason to worry?

It seems that Cophy-makers use a huge diversity of IDE, and that we are still a minority to use Git-based version control.

PyCharm-Matlab people: who are you, what are your networks?🕵️

0.6 Towards a straightforward solution

Correlation does not imply causation, but those who are still not using Git may still need to install Visual Studio Code.

1 Tutorial!

Be reassured: following it won’t break your computer, it won’t require much space and it is safe.

1.1 Visual Studio Code

Click here for the main installer and then get the next three extension:

If you’re waiting, you can get more extensions: GitGraph (to help dealing with messy Git), Rainbow CSV (to help reading CSVs), Jupyter

1.2 Wait, how is this going to help with writing?

Because it writing in VS Code is actually possible, and amazing, thanks to the Markdow syntax combined with another really powerful tool, Quarto. ::: {.incremental style=“font-size: 80%;”} - Huge improvement in the accessibility of Markdown thanks to a Word-like editor.

  • Amazing reference management logics (flawless integration with Zotero, Pubmed, Crossref, fromDOI, etc.)

  • Possibility to write: code, articles, books, websites and.. simple presentations like this one! ::: Click here to get Quarto itself and here to get the VScode extension.

1.3 Final step before discovering Quarto

Now, we’ll just need to make sure that everyone has:

  • Git

  • Github CLI (optional but useful if you have a Github account)

Once it’s done, just close and restart.

1.4 Let’s experiment with our collaboration pipeline

Since we are on the CRNL network, we can easily connect to the cluster using SSH.

To do so, just click the bottom left button of VS code

Choose “Connect to host” and enter:

ssh prenom.nom@10.69.168.62

Then enter your CRNL credentials (same as those who get you in the wiki!)

R. Ligneul - COPHY - 10.10.23